Skip to content

Upgrade MiniMax default model to M3#177

Open
octo-patch wants to merge 3 commits into
The-Pocket:mainfrom
octo-patch:feature/add-minimax-provider
Open

Upgrade MiniMax default model to M3#177
octo-patch wants to merge 3 commits into
The-Pocket:mainfrom
octo-patch:feature/add-minimax-provider

Conversation

@octo-patch
Copy link
Copy Markdown

@octo-patch octo-patch commented Mar 17, 2026

Summary

Upgrade the MiniMax provider's default model from M2.7 to M3, while keeping M2.7 and M2.7-highspeed available as alternatives.

Changes

File Change
utils/call_llm.py Default model bumped from MiniMax-M2.7 to MiniMax-M3
.env.sample Default-model comment updated to M3
README.md MiniMax auto-config description now references M3
tests/test_call_llm.py Default-model assertions updated to expect M3

Why

MiniMax M3 is the latest generation model with a 512K context window, up to 128K output, and image input support. Bumping the default gives users a more capable out-of-the-box experience.

MiniMax-M2.7 and MiniMax-M2.7-highspeed are still selectable via the MINIMAX_MODEL env var for users who prefer them.

Testing

  • 15 unit tests pass (provider detection, defaults, request construction, caching, temperature clamping)
  • 3 live integration tests skipped (no MINIMAX_API_KEY in CI)
  • Existing Gemini/generic provider behavior unchanged

PR Bot and others added 3 commits March 17, 2026 19:55
- Auto-detect MiniMax when MINIMAX_API_KEY is set (no LLM_PROVIDER needed)
- Built-in defaults: model (MiniMax-M2.5), base URL, temperature range
- Temperature clamping to MiniMax's accepted (0.01, 1.0] range
- Custom model/base URL overrides via MINIMAX_MODEL / MINIMAX_BASE_URL
- 15 unit tests + 3 live integration tests
- Updated .env.sample and README with MiniMax configuration
- Set MiniMax-M2.7 as default model (was M2.5)
- Update highspeed model reference to MiniMax-M2.7-highspeed
- Keep all previous models as available alternatives via env var
- Update related unit tests and documentation
- Upgrade default model from MiniMax-M2.7 to MiniMax-M3
- Keep MiniMax-M2.7-highspeed as alternative
- Update related tests, README, and .env.sample
- All 15 unit tests pass
@octo-patch octo-patch changed the title Add MiniMax as first-class LLM provider with auto-detection Upgrade MiniMax default model to M3 Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant